Cloud infrastructure for isolation and run-time behavioral tuning through configuration externalization

ABSTRACT

Embodiments generally relate to a cloud computing infrastructure and method of operating the same including at least: receiving a configuration file from a configuration repository; receiving a request from a first device to configure an application rule set of one or more nodes based on the configuration file; transmitting the request to a receiver node selected from the one or more nodes; generating a notification alerting the one or more nodes that the request is stored on a database; distributing the configuration file to a subset of the one or more nodes based on receipt of an access request from the one or more nodes; and updating the application rule set of the subset of the one or more nodes based on the configuration file.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/821,739, filed on Mar. 17, 2020, the contents of which isincorporated by reference herein.

TECHNICAL FIELD

An embodiment of the present disclosure relates generally to a cloudcomputing infrastructure, and more particularly to a cloud computinginfrastructure for isolation and run-time behavioral tuning throughconfiguration externalization.

BACKGROUND

Rule Management Systems (RMS) have become widely used to implementvarious computing functions including implementing rules, policies, andguidelines for operation of computing devices. One problem when usingRMS systems in cloud computing environments is the inability to updatevarious computing devices implementing the rules, policies, andguidelines of the RMS without impacting the other devices. Despitetechnological advancements, current technologies still lack the abilityto adequately update computing devices in cloud-based RMS systems.Accordingly, there remains a need for improved techniques for updatingcomputing devices in cloud-based RMS systems.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form a partof the specification, illustrate embodiments of the present disclosureand, together with the description, further serve to explain theprinciples of the disclosure and to enable a person skilled in thepertinent art to make and use the disclosure.

FIG. 1 is an example cloud computing system for isolation and run-timebehavioral tuning through configuration externalization according toembodiments.

FIG. 2 is an example block diagram of the components of the systemaccording to embodiments.

FIG. 3 is an example control flow of the system according toembodiments.

FIG. 4 is an example method of operating the system according toembodiments.

DETAILED DESCRIPTION

Embodiments of the disclosure provide a system for updating andconfiguring an application rule set in a cloud computing environment,independently from a software download process for one or more nodes.This separation provides the system the ability to isolate the rules,policies, and guidelines that the nodes are to implement from theunderlying functions that provide the operational functionality of thenodes. As a result, the software which makes the nodes operate isseparated from the rules, policies, and guidelines implemented by thenodes implementing the RMS.

The following embodiments are described in sufficient detail to enablethose skilled in the art to make and use the disclosure. It is to beunderstood that other embodiments would be evident based on the presentdisclosure, and that system, process, or mechanical changes may be madewithout departing from the scope of an embodiment of the presentdisclosure.

In the following description, numerous specific details are given toprovide a thorough understanding of embodiments. However, it will beapparent that embodiments may be practiced without these specificdetails. In order to avoid obscuring an embodiment, some well-knowncircuits, system configurations, and process steps are not disclosed indetail.

The drawings showing embodiments of the system are semi-diagrammatic,and not to scale. Some of the dimensions are for the clarity ofpresentation and are shown exaggerated in the drawing figures.Similarly, although the views in the drawings are for ease ofdescription and generally show similar orientations, this depiction inthe figures is arbitrary for the most part. Generally, the system can beoperated in any orientation.

Certain embodiments have other steps or elements in addition to or inplace of those mentioned. The steps or elements will become apparent tothose skilled in the art from a reading of the following detaileddescription when taken with reference to the accompanying drawings.

The term “module” or “unit” referred to herein can include software,hardware, or a combination thereof in an embodiment of the presentdisclosure in accordance with the context in which the term is used. Forexample, the software can be machine code, firmware, embedded code, orapplication software. Also for example, the hardware can be circuitry, aprocessor, a special purpose computer, an integrated circuit, integratedcircuit cores, a pressure sensor, an inertial sensor, amicroelectromechanical system (MEMS), passive devices, or a combinationthereof. Further, if a module or unit is written in the system orapparatus claims section below, the module or unit is deemed to includehardware circuitry for the purposes and the scope of the system orapparatus claims.

The term “service” or “services” referred to herein can include acollection of modules or units. A collection of modules or units can bearranged, for example, in software or hardware libraries or developmentkits in an embodiment of the present disclosure in accordance with thecontext in which the term is used. For example, the software or hardwarelibraries and development kits can be a suite of data and programmingcode, for example pre-written code, classes, routines, procedures,scripts, configuration data, or a combination thereof, that can becalled directly or through an application programming interface (API) tofacilitate the execution of the functions disclosed.

The modules, units, and services in the following description of theembodiments can be coupled to one another as described or as shown. Thecoupling can be direct or indirect, without or with intervening itemsbetween coupled modules, units, or services. The coupling can be byphysical contact or by communication between modules, units, orservices.

Referring now to FIG. 1, therein is shown an example cloud computingsystem 100 (or “system 100”) for isolation and run-time behavioraltuning through configuration externalization according to embodiments.The system 100 is a cloud computing platform designed to managecommunications between one or more computing devices that operate withinthe system 100. The system 100 provides a platform that facilitatescommunication regarding, notification of, distribution of, andimplementation of messages, configurations, and updates between thedevices or a subset of the devices. Further details regarding thecommunication, notification, distribution, and implementation ofmessages, configurations, and updates will be discussed further below.

In one embodiment, the system 100 can include a first device 102, suchas a client device or a server, connected to a second device 106, suchas a client device or server. In one embodiment, the first device 102and the second device 106 can be standalone devices or a distribution ofdevices, such as a distribution of client devices or servers. Ifimplemented as a distribution of devices, the distribution can includeone or more further client devices or servers. Such further clientdevices or servers can be implemented as one or more nodes 108 of thefirst device 102 or the second device 106. For example, if the seconddevice 106 is implemented as a distribution of devices, in oneembodiment, the second device 106 can include one or more servers whichcan be the nodes 108. In one embodiment, the nodes 108 can, instead ofbeing one or more client devices or servers, can be one or more servicesrunning on the first device 102 or the second device 106, such that eachof the nodes 108 can be software running within the first device 102 orthe second device 106 to perform a particular function for the firstdevice 102 or the second device 106.

In one embodiment, the first device 102 and the second device 106 cancommunicate with each other through a communication path 104, such as awireless or wired network. For example, the first device 102 can be ofany of a variety of devices, such as a smart phone, a cellular phone, apersonal digital assistant, a tablet computer, a notebook computer, alaptop computer, a desktop computer, or a combination thereof. The firstdevice 102 can couple, either directly or indirectly, to thecommunication path 104 to communicate with the second device 106 or canbe a stand-alone device.

The second device 106 can be any of a variety of centralized ordecentralized computing devices. For example, the second device 106 canbe a laptop computer, a desktop computer, grid-computing resources, avirtualized computing resource, cloud computing resources, routers,switches, peer-to-peer distributed computing devices, a server, a serverfarm, or a combination thereof. The second device 106 can be centralizedin a single room, distributed across different rooms, distributed acrossdifferent geographical locations, or can be embedded within atelecommunications network. The second device 106 can couple with thecommunication path 104 to communicate with the first device 102 or canbe a stand-alone device.

For illustrative purposes, the system 100 is shown with the first device102 as a client device, although it is understood that the system 100can have the first device 102 as a different type of device. Forexample, the first device 102 can be a server. Also for illustrativepurposes, the system 100 is shown with the second device 106 as aserver, although it is understood that the system 100 can have thesecond device 106 as a different type of device. For example, the seconddevice 106 can be a client device.

For brevity of description in the embodiments discussed below, the firstdevice 102 will be described as a client device and the second device106 will be described as a server device. The embodiments disclosedherein, however, are not limited to this selection for the type ofdevices. The selection is an example of an embodiment.

Also for illustrative purposes, the system 100 is shown with the firstdevice 102 and the second device 106 as end points of the communicationpath 104, although it is understood that the system 100 can have adifferent partition between the first device 102, the second device 106,and the communication path 104. For example, the first device 102 andthe second device 106 can also function as part of the communicationpath 104.

The communication path 104 can span and represent a variety of networksand network topologies. For example, the communication path 104 caninclude wireless communication, wired communication, opticalcommunication, ultrasonic communication, or a combination thereof. Forexample, satellite communication, cellular communication, Bluetooth,Infrared Data Association standard (IrDA), wireless fidelity (WiFi), andworldwide interoperability for microwave access (WiMAX) are examples ofwireless communication that can be included in the communication path104. Cable, Ethernet, digital subscriber line (DSL), fiber optic lines,fiber to the home (FTTH), and plain old telephone service (POTS) areexamples of wired communication that can be included in thecommunication path 104. Further, the communication path 104 can traversea number of network topologies and distances. For example, thecommunication path 104 can include direct connection, personal areanetwork (PAN), local area network (LAN), metropolitan area network(MAN), wide area network (WAN), or a combination thereof.

Referring now to FIG. 2, therein is shown an example block diagram ofthe components 200 of the system 100 according to embodiments. Thecomponents 200 shown can be used or implemented in any of the devices ofthe system 100. For example, the components 200 can be used orimplemented in the first device 102, the second device 106, the nodes108, or a combination thereof.

In one embodiment, the components 200 can include a control unit 202, astorage unit 206, a communication unit 216, and a user interface 212.The control unit 202 can include a control interface 204. The controlunit 202 can execute a software 210 to provide some or all of theintelligence of the system 100. The control unit 202 can be implementedin a number of different ways. For example, the control unit 202 can bea processor, an application specific integrated circuit (ASIC), anembedded processor, a microprocessor, a hardware control logic, ahardware finite state machine (FSM), a digital signal processor (DSP), afield programmable gate array (FPGA), or a combination thereof.

The control interface 204 can be used for communication between thecontrol unit 202 and other functional units or devices of the system100. The control interface 204 can also be used for communication thatis external to the functional units or devices of the system 100. Thecontrol interface 204 can receive information from the functional unitsor devices of the system 100, or from remote devices 220, or cantransmit information to the functional units or devices of the system100 or to remote devices 220. The remote devices 220 refer to functionalunits or devices external to the system 100.

The control interface 204 can be implemented in different ways and caninclude different implementations depending on which functional units ordevices of the system 100 or remote devices 220 are being interfacedwith the control unit 202. For example, the control interface 204 can beimplemented with a pressure sensor, an inertial sensor, amicroelectromechanical system (MEMS), optical circuitry, waveguides,wireless circuitry, wireline circuitry to attach to a bus, anapplication programming interface, or a combination thereof. The controlinterface 204 can be connected to a communication infrastructure 222,such as a bus, to interface with the functional units or devices of thesystem or remote devices 220.

The storage unit 206 can store the software 210. For illustrativepurposes, the storage unit 206 is shown as a single element, although itis understood that the storage unit 206 can be a distribution of storageelements. Also for illustrative purposes, the storage unit 206 is shownas a single hierarchy storage system, although it is understood that thestorage unit 206 can be in a different configuration. For example, thestorage unit 206 can be formed with different storage technologiesforming a memory hierarchal system including different levels ofcaching, main memory, rotating media, or off-line storage. The storageunit 206 can be a volatile memory, a nonvolatile memory, an internalmemory, an external memory, or a combination thereof. For example, thestorage unit 206 can be a nonvolatile storage such as nonvolatile randomaccess memory (NVRAM), Flash memory, disk storage, or a volatile storagesuch as static random access memory (SRAM) or dynamic random accessmemory (DRAM).

The storage unit 206 can include a storage interface 208. The storageinterface 208 can be used for communication between the storage unit 206and other functional units or devices of the system 100. The storageinterface 208 can also be used for communication that is external to thesystem 100. The storage interface 208 can receive information from theother functional units or devices of the system 100 or from remotedevices 220, or can transmit information to the other functional unitsor devices of the system 100 or to remote devices 220. The storageinterface 208 can include different implementations depending on whichfunctional units or devices of the system 100 or remote devices 220 arebeing interfaced with the storage unit 206. The storage interface 208can be implemented with technologies and techniques similar to theimplementation of the control interface 204.

The communication unit 216 can enable communication to devices of thesystem 100 or to remote devices 220. For example, the communication unit216 can permit the first device 102 to communicate with the seconddevice 106, or can permit the nodes 108 to communicate with one another,or to the first device 102. The communication unit 216 can furtherpermit the devices of the system 100 to communicate with remote devices220 such as an attachment, such as a peripheral device, through thecommunication path 104. The communication unit 216 can also function asa communication hub allowing the first device 102, the second device106, the nodes 108, or a combination thereof to function as part of thecommunication path 104 and not be limited to be an end point or terminalunit to the communication path 104. The communication unit 216 caninclude active and passive components, such as microelectronics or anantenna, for interaction with the communication path 104.

The communication unit 216 can include a communication interface 218.The communication interface 218 can be used for communication betweenthe communication unit 216 and other functional units or devices of thesystem 100 or to remote devices 220. The communication interface 218 canreceive information from the other functional units or devices of thesystem 100, or from remote devices 220, or can transmit information tothe other functional units or devices of the system 100 or to remotedevices 220. The communication interface 218 can include differentimplementations depending on which functional units or devices are beinginterfaced with the communication unit 216. The communication interface218 can be implemented with technologies and techniques similar to theimplementation of the control interface 204.

The user interface 212 can present information generated by the system100. In one embodiment, the user interface 212 allows a user of thesystem 100 to interface with the devices of the system 100 or remotedevices 220. The user interface 212 can include an input device and anoutput device. Examples of the input device of the user interface 212can include a keypad, buttons, switches, touchpads, soft-keys, akeyboard, a mouse, or any combination thereof to provide data andcommunication inputs. Examples of the output device can include adisplay interface 214. The control unit 202 can operate the userinterface 212 to present information generated by the system 100. Thecontrol unit 202 can also execute the software 210 to presentinformation generated by the system 100, or to control other functionalunits of the system 100. The display interface 214 can be any graphicaluser interface such as a display, a projector, a video screen, or anycombination thereof.

The components 200 can be optimized for implementing an embodiment in amultiple device embodiment wherein the first device 102, the seconddevice 106, the nodes 108, or a combination thereof are required toimplement the one or more functions of the system 100. For example, ifthe first device 102 and the second device 106 are to each provide somefunctionality of the system 100, the control unit 202 of either thefirst device 102 or the second device 106 can execute the software 210of the first device 102, the second device 106, or a combination thereofto implement the functionality of the system 100.

For illustrative purposes, the system 100 is described by operation ofthe first device 102, the second device 106, or the nodes 108. It isunderstood that the first device 102, the second device 106, or thenodes 108 can operate any of the modules, units, and functions of thesystem 100.

Referring now to FIG. 3, therein is shown an example control flow 300 ofthe system 100 according to embodiments. For brevity of description, thecontrol flow 300 in FIG. 3 will be described as functioning on thesecond device 106, in an embodiment where the second device 106 isimplemented to include one or more nodes 108. This, however, is merelyexemplary. In another embodiment, the control flow 300, or some of itsfunctions can be implemented on the first device 102.

In one embodiment, the control flow 300 can be implemented with modules,sub-modules, or services. In one embodiment, the control flow 300 caninclude a monitor module 306, a message service 308, and a configurationservice 310. In one embodiment, the monitor module 306 can couple to themessage service 308 via a network 316, where the network 316 includesthe one or more nodes 108. The message service 308 can further couple tothe configuration service 310 via the network 316.

The monitor module 306 can enable the receipt of a request 318 from adevice, for example the first device 102. In one embodiment, the monitormodule 306 can function by implementing a pull model. The pull modelrefers to a mechanism or process by which the monitor module 306continuously checks for the request 318 from devices of the system 100,for example the first device 102, to determine whether any of thedevices of the system 100 are requesting an update of the applicationrule set 320. In one embodiment, the pull model can function by sendingpull requests at specified times to one or more devices of the system100 to determine whether the devices of the system 100 are requesting anupdate to the application rule set 320. The pull requests can be in theform of a signal, data structure, data packet, or a combination thereof.For example, in one embodiment, the monitor module 306 can send pullrequests every “X” minutes, where X is an integer, to the devices of thesystem. In one embodiment, the monitor module 306 can further functionby receiving the request 318 from the devices of the system 100 withoutsending pull requests but rather obtaining the request 318 by thedevices of the system 100 when a user of the system 100 makes therequest 318 in real-time. Real-time refers to the actual time duringwhich the user of the system 100 makes the request 318.

In one embodiment, the request 318 can trigger or cause the update andconfiguration of an application rule set 320 of the second device 106 orthe nodes 108 or a subset thereof. The request 318 can be in the form ofa signal, variable, data, a data structure, an instruction, or acombination thereof. In one embodiment, the request 318 can be sent fromthe first device 102 to the second device 106. For example, in oneembodiment, the request 318 can be part of the data input by a user ofthe first device 102 using a webpage, web form, or a combinationthereof. In another embodiment, the request 318 can be part of the dataor instructions within a computer file, such as a text file or a commaseparated value file. In another embodiment, the request 318 can be avariable or data structure passed by a computer program and transmittedfrom the first device 102 to the second device 106 via the communicationpath 104.

The application rule set 320 refers to a set of guidelines or logic thatdefine or constrain the operation of the second device 106 or nodes 108.The application rule set 320 can be, for example, computer implementedguidelines or rules that can be implemented as a part of a rulemanagement system (RMS), and can include policies, requirements, andconditional statements that are implemented to determine actions to betaken by the second device 106 or the nodes 108. In one embodiment, theapplication rule set 320 can be implemented as a set of computer rulesin a computer file, a computer program, a computer program function, acomputer program class, a computer program object, or a combinationthereof on the second device 106 or the nodes 108.

By way of example to show the operation of the application rule set 320,in one embodiment, the second device 106 or the nodes 108 or a subsetthereof can form part of the backend server infrastructure of an entity,for example a corporation or an institution. The second device 106 orthe nodes 108 can together or individually perform a specified functionor specified functions. For example, in the case where the entity is acorporation that, for example as a part of its operations, performsadvertising campaigns in which products and services are advertised tocustomers, potential customers, or other external users, the functionsof the second device 106 or the nodes 108 or a subset thereof can be toexecute the advertising campaigns, wherein the second device 106 or thenodes 108 or a subset thereof can distribute information, in the form ofemail communications, text messages, push notifications, or similarcommunications regarding products or services to customers, potentialcustomers, or external users.

In the aforementioned example, the application rule set 320 can providethe rules, guidelines, or policies regarding the method of communicationto the customers, potential customers, or external users. For example,the application rule set 320 can determine the rules, guidelines, orpolicies regarding which customers, potential customers, or externalusers the second device 106 or the nodes 108 or a subset thereof shouldcontact and under what conditions. For example, if a customer would liketo be contacted regarding one service or product but not another serviceor product, the application rule set 320 can provide the rules,guidelines, or policies that can be implemented by the second device 106or the nodes 108 or a subset thereof to fulfill the conditions forcontacting the customer, potential customer, or external user. Inanother example, if the customer would like to be contacted at aparticular frequency, for example, once a day, once a week, or once amonth, then the application rule set 320 can provide the rules,guidelines, or policies that can be implemented by the second device 106or the nodes 108 or a subset thereof to fulfill the frequency at whichthe customer is contacted. The aforementioned functions of theapplication rule set 320 are merely exemplary and not meant to belimiting. The example is meant to demonstrate an example implementationof the application rule set 320 and the types of rules the applicationrule set 320 can implement. The application rule set 320 can be used toperform other functions in different implementations.

In one embodiment, the application rule set 320 can be stored on, andexecuted by, the second device 106 or the nodes 108 or a subset thereofto implement the rules, guidelines, or policies of the RMS. In oneembodiment, the application rule set 320 can have different versions. Inone embodiment, depending on what device the application rule set 320 isstored on, different versions of the application rule set 320 can exist.For example, in one embodiment, one version of the application rule set320 can be stored on one of the nodes 108 of the one or more nodes 108,while another version of the application rule set 320 can be stored onanother node of the one or more nodes 108.

In one embodiment one version of the application rule set 320 can bestored on and retrieved from, a configuration repository 302. Theconfiguration repository 302 refers to a database or storage that canstore a version of the application rule set 320 and distribute theversion of the application rule set 320 to other devices. In oneembodiment, the configuration repository 302 can be implemented usingthe same technologies and same techniques as the storage unit 206. Theconfiguration repository 302 can be part of second device 106 or beexternal to the second device 106.

In one embodiment, the configuration repository 302 can transmit theversion of the application rule set 320 stored thereon to one or moredevices of the system 100. For example, in the embodiment shown in thisFIG. 3, the application rule set 320 is shown to be transmitted by theconfiguration repository 302 to the second device 106. In oneembodiment, the application rule set 320 can specifically be transmittedto the configuration service 310 of the second device 106. Theconfiguration service 310 refers to a storage and distribution serviceof the second device 106 that can store and distribute the applicationrule set 320 received from the configuration repository 320 for furtherdistribution to devices of the system 100.

In one embodiment, the configuration service 310 can distribute theapplication rule set 320 to the nodes 108 upon the occurrence of anevent or alert requesting or demanding the distribution of theapplication rule set 320. For example, the event or alert can be in theform of a notification generated by the second device 106 or the nodes108 or a subset thereof indicating that the request 318 sent from thefirst device 102 was received by the second device 106 or one or morenodes 108, or that the request 318 was received by a service of thesecond device 106, such as the message service 308 and stored in adatabase. In another embodiment, the event or alert can be in the formof a periodic timing criteria such as a real-time, hourly, weekly,daily, etc. signal generated by the second device 106 or the nodes 108or a subset thereof at which time the application rule set 320 isrequested from the configuration repository 302 by the configurationservice 310. For example, the specified periodic timing criteria can beto send a signal requesting the application rule set 320 every hour,once a week, once a day, etc. In another embodiment, the applicationrule set 320 can be transmitted in an ad hoc manner from theconfiguration repository 302 based on a trigger condition by one of thedevices of the system 100 or by a third party, such as by a systemadministrator of the system 100. For example, in one embodiment, theapplication rule set 320 can be transmitted based on a systemadministrator requesting or demanding that the application rule set 320be transmitted.

In one embodiment, the configuration service 310 can implement a pushmodel to distribute the application rule set 320 to the devices of thesystem 100. The push model refers to a mechanism or process by which theconfiguration service 310, upon receipt of an application rule set 320from the configuration repository 302 sends a signal, data structure, ora combination thereof to a module of the system 100, for example themonitor module 306 indicating that an application rule set 320 has beenreceived and is ready to be installed on the devices of the system 100.In one embodiment, the push model can function by sending the signal,data structure, or a combination thereof in real-time to the modules ofthe system 100 upon the receipt of the application rule set 320 from theconfiguration repository 302. In another embodiment, the push module canfunction by sending the signal, data structure or a combination thereofat a specified time or as part of a batch process to the modules of thesystem 100. The sending of the signal, data structure, or a combinationthereof by the configuration service 310 can trigger or cause the updateand configuration of an application rule set 320 of the second device106 or the nodes 108 or a subset thereof.

In one embodiment, the application rule set 320 can be transmitted usinga configuration file 304. The configuration file 304 refers to acomputer file or computer program that can be used to transmit theapplication rule set 320. The configuration file 304 can be in the formof a text file, an executable file, an object file, a data file, ahyperlink, or a combination thereof. For example, if the configurationfile 304 is in the form of a text file, the application rule set 320 canbe sent as a set of rules or conditional statements embedded in the textfile. If, however, the configuration file 304 is an executable file oran object file, the application rule set 320 can be sent as a set ofrules or functions containing the rules as conditional statements to beexecuted once the executable file or the object file is executed by aprocessor, an operating system, or a combination thereof.

Continuing with the example of the control flow 300, and assuming theembodiment where a pull model is implemented and from when the monitormodule 306 receives the request 318 from the first device 102, in oneembodiment, the monitor module 306, upon receipt of the request 318 canfurther enable the transmission of the request 318 to a receiver node324 chosen from the nodes 108 to further receive the request 318. Thereceiver node 324 refers to a node from amongst the one or more nodes108 that can receive the request 318 from the monitor module 306 and canfurther transmit the request 318 to the message service 308 for storageon a database associated with, or that can be accessed by, the messageservice 308. The receiver node 324 can act as a gateway or bridgebetween the monitor module 306, the nodes 108, and the services of thesecond device 106, such as the message service 308 and the configurationservice 310.

In one embodiment, the monitor module 306 can determine which node fromamongst the one or more nodes 108 will be the receiver node 324. In oneembodiment, the receiver node 324 can be selected based on a selectioncriteria. In one embodiment, the selection criteria can be, for example,based on a network traffic to and from the nodes 108. For example, inone embodiment, the monitor module 306 can analyze a network traffic toand from the nodes 108 and determine which node from among the one ormore nodes 108 has the least amount of network traffic going to and fromthe node, in terms of bits or bytes of data going to and from the nodeover a period of time, and select the node with the least amount ofnetwork traffic as the receiver node 324. For example, if the networktraffic is below a threshold value, for example below “X” number of bitsor bytes to the node per second, where “X” is an integer, the monitormodule 306 can select a node falling below the threshold value as thereceiver node 324. In another embodiment, the selection criteria canfurther be, for example, based on analyzing a processor speed, processorbandwidth, a node storage capacity, or a combination thereof amongst thenodes 108. For example, in one embodiment, the monitor module 306 canselect the receiver node 324 as the node from amongst the nodes 108 thathas the fastest processing speed, the most bandwidth to process data,the most storage capacity, or a combination thereof.

In one embodiment, once the monitor module 306 selects the receiver node324 and transmits the request 318 to the receiver node 324, the receivernode 324 can further transmit or route the request 318 to the messageservice 308. The message service 308 refers to a service of the seconddevice 106 that acts as a message repository for messages to and fromdifferent devices, functional units, or services of the system 100. Themessages can be in the form of, for example, commands, instructions,files, communications, configurations, or a combination thereof betweendevices, functional units, or services to be distributed between thenodes 108, the functional units of the second device 106, or services ofthe second device 106, or a combination thereof.

In one embodiment, once the receiver node 324 receives and transmits therequest 318 to the message service 308, the message service 308 canstore the request 318 in a database. The database can be implementedwith similar technologies and techniques as the storage unit 206. In oneembodiment, once the request 318 is stored in the database, the messageservice 308 can generate a notification to other functional units of thesecond device 106, the nodes 108, or a combination thereof indicatingthat the request 318 has been made by the first device 102 to update andconfigure the application data set 320 of the nodes 108 or a subsetthereof.

In one embodiment, based on the notification, the nodes 108 or a subsetthereof can generate an access request to access the configurationservice 310 so the nodes 108 or a subset thereof can access theconfiguration file 304 containing the application rule set 320 stored onthe configuration service 310. The access request can be in the form ofa signal, variable, data, a data structure, an instruction, or acombination thereof. In one embodiment, once the access request isreceived by the configuration service 310, the configuration service 310can distribute the configuration file 304 to the nodes 108 or a subsetthereof that made the access request by transmitting the configurationfile 304, including the application rule set 320 contained in theconfiguration file 304, to the nodes 108 or a subset thereof.

In one embodiment, the nodes 108 or a subset thereof that made theaccess request can receive the configuration file 304 including theapplication rule set 320, and based on the application rule set 320received, can update and configure the previous version of theapplication rule set 320 with the updated application rule set 320received from the configuration service 310, by for example replacingand storing the updated version of the configuration file 304 in theirstorage and using the same to update their rules, policies, orguidelines for implementing functions for the RMS. In one embodiment, ifthe configuration file 304 is an executable file or object file, thenodes 108 or a subset thereof can update and configure their rules,policies, or guidelines by executing the configuration file 304 toimplement the application rule set 320. In one embodiment, if theconfiguration file 304 is a text file, the nodes 108 or a subset thereofcan store the text file, access the text file, and parse the text fileto access the rules, policies, or guidelines when implementing thefunctions of the RMS.

By way of example, referring back to the example and embodiment wherethe nodes 108 are part of a system for executing advertising campaigns,and each node amongst the one or more nodes 108 is responsible forcommunicating with a set of customers, potential customers, or externalusers in a particular manner to implement the advertising campaign, theapplication rule set 320 for each of the nodes 108 or a subset thereofcan be updated and changed, or modified such that the rules, policies,or guidelines for each node to communicate with a customer, a potentialcustomer, or an external user can be varied. For example, if one node,for example “NODE A” previously could only communicate with an externaluser who was within a certain geographic region, for example “REGION A,”and only via “EMAIL,” the application rule set 320 of the node can beupdated, modified, or changed such that the NODE A can now contactexternal users from REGION A and a new geographic region, for example“REGION B,” and in addition to communicating via EMAIL can communicateusing the additional communication platform of “TEXT MESSAGE.” As aresult, the application rule set 320 can control a method ofcommunication by the nodes 108 to the customers, potential customers, orexternal users. In one embodiment, the application rule set 320 of eachnode from amongst the one or more nodes 108 can vary such that therules, policies, and guidelines for the node can be different from thoseof the other nodes 108. The aforementioned is merely an example of a wayin which the application rule set 320 can be updated and configured foreach of the nodes 108 or a subset thereof and is not meant to belimiting. Other rules, policies, and guidelines can be updated in asimilar manner as described above.

In one embodiment, the nodes 108 can run the software 210 to providepart of their intelligence. In one embodiment, the software 210 can bestored in a source code repository 312 and can be transmitted andreceived by the nodes 108 via a download process. The source coderepository 312 refers to a storage that can store and deploy thesoftware 210 for the nodes 108. In one embodiment, the source coderepository 312 can be implemented using similar technologies andtechniques as the storage unit 206. Continuing with the example, tofacilitate the download process a deployment module 314 can be used. Thedeployment module 314 can interface between the source code repository312 and the nodes 108 to facilitate the download of the software 210from the source code repository 312 to the nodes 108. In one embodiment,the deployment module 314 can, for example, provide the protocolfunctions and the APIs necessary to facilitate the download of thesoftware 210 from the source code repository 312 to the nodes 108. Afeature of the disclosure is that the updating and configuration of theapplication rule set 320 is independent from the download process of thesoftware 210 for the nodes 108. This separation provides the system 100the ability to isolate the rules, policies, and guidelines that thenodes 108 are to implement from the underlying functions that providethe operational functionality of the nodes 108. As a result, thesoftware 210 which makes the nodes 108 operate is separated from therules, policies, and guidelines implemented by the nodes 108implementing the RMS.

The methods, modules, units, and components implementing theabove-described system 100 significantly improve the ability of thesystem 100 to implement rules, policies, and guidelines of a cloud-basedRMS. Specifically, it has been discovered that by implementing thesystem 100 as described above, the system 100 can provide an efficientcloud computing platform that can be used to modularize and isolate theimpact of updates to devices of the system 100. For example, updates tothe one or more nodes 108 can be isolated from one another based on thesystem 100 having the ability to update and configure the applicationrule set 320 of one node without impacting the operation of the othernodes 108.

The system 100 as described above can be used to implement multiplefunctionalities on the nodes 108 of the system 100 without the need toupgrade or update every node of the system 100 and, as a result,minimizes the impact of different devices of the cloud-based RMS on oneanother. The system 100 described above also improves the efficiency ofa cloud computing RMS based on the ability to upgrade certain devices ofthe RMS without causing downtime to other devices of the cloud-basedRMS.

Additionally, the system 100 significantly improves the ability tocontrol each device of the system 100 because each device can beupgraded and configured individually, thus resulting in betterfine-tuning of the system 100. The system 100 as described above canalso provide greater redundancy and stability because, if one of thenodes 108 fails, another node can be updated with an application ruleset 320 providing similar functionality as the failed node. In this way,no interruption of services will be incurred by an entity implementing aRMS using the above-disclosed system 100.

The system 100 has been described with module or service functions ororder as an example. The system 100 can partition the modules orservices differently or order the modules or services differently. Forexample, the software 210 can include the modules or services for thesystem 100. As a specific example, the software 210 can include themonitor module 306, the message service 308, the configuration service310, the deployment module 314, and associated sub-modules includedtherein.

The control unit 202 can execute the software 210 to operate the modulesor services. For example, the control unit 202 can execute the software210 to implement the monitor module 306, the message service 308, theconfiguration service 310, the deployment module 314, and associatedsub-modules included therein.

The modules described in this application can be implemented asinstructions stored on a non-transitory computer readable medium to beexecuted by the control unit 202. The non-transitory computer readablemedium can include the storage unit 206. The non-transitory computerreadable medium can include non-volatile memory, such as a hard diskdrive, non-volatile random access memory (NVRAM), solid-state storagedevice (SSD), compact disk (CD), digital video disk (DVD), or universalserial bus (USB) flash memory devices. The non-transitory computerreadable medium can be integrated as a part of the system 100 orinstalled as a removable portion of the system 100.

Referring now to FIG. 4, therein is shown an example method 400 ofoperating the system according to embodiments.

In step 402, a configuration file (such as configuration file 304,discussed above) is received from a configuration repository. Theconfiguration file contains instructions for configuring an applicationrule set (such as application rule set 320) of one or more nodes (suchas nodes 108) in a network. For example, the configuration file can bereceived by the communication unit (such as communication unit 216) ofthe second device (such as second device 106) via the communication path(such as communication path 104).

In step 404, a request (such as request 318) is received from a firstdevice (such as first device 102) to configure the application rule setof the one or more nodes based on the configuration file. For example,the request from the first device can be received by the communicationunit of the second device via the communication path.

In step 406, the request is transmitted to a receiver node (such asreceiver node 324) selected from the one or more nodes. The receivernode then further transmits the request to a message service (such asmessage service 308) for storage on a database. For example, the requestcan be transmitted by the communication unit of the receiver node viathe communication path.

In step 408, a notification can be generated. In an embodiment, thenotification alerts the one or more nodes that the request is stored onthe database. For example, the notification can be generated by acontrol unit (such as control unit 202) of the second device or thereceiver node, in conjunction with the message service.

In step 410, the configuration file is distributed to a subset of theone or more nodes based on receipt of an access request from the one ormore nodes in response to the notification. In an embodiment, the accessrequest requests access to the configuration file. For example, thedistribution can be performed by the control unit of the second deviceor the receiver node, in conjunction with a configuration service (suchas configuration service 310).

In step 412, the application rule set of the subset of the one or morenodes is updated based on the configuration file. For example, theupdating can be performed by the control unit of the second device orthe nodes by updating a software (such as software 210) of the nodeswith the application rule set found in the configuration file.

The above detailed description and embodiments of the disclosed system100 are not intended to be exhaustive or to limit the disclosed system100 to the precise form disclosed above. While specific examples for thesystem 100 are described above for illustrative purposes, variousequivalent modifications are possible within the scope of the disclosedsystem 100, as those skilled in the relevant art will recognize. Forexample, while processes and methods are presented in a given order,alternative implementations may perform routines having steps, or employsystems having processes or methods, in a different order, and someprocesses or methods may be deleted, moved, added, subdivided, combined,or modified to provide alternative or sub-combinations. Each of theseprocesses or methods may be implemented in a variety of different ways.Also, while processes or methods are at times shown or described asbeing performed in series, these processes or blocks may instead beperformed or implemented in parallel, or may be performed at differenttimes.

The resulting method, process, apparatus, device, product, and system iscost-effective, highly versatile, and accurate, and can be implementedby adapting components for ready, efficient, and economicalmanufacturing, application, and utilization. Another aspect of anembodiment is that it valuably supports and services the historicaltrend of reducing costs, simplifying systems, and increasingperformance.

These and other valuable aspects of the embodiments consequently furtherthe state of the technology to at least the next level. While thedisclosed embodiments have been described as the best mode ofimplementing the system 100, it is to be understood that manyalternatives, modifications, and variations will be apparent to thoseskilled in the art in light of the descriptions herein. Accordingly, itis intended to embrace all such alternatives, modifications, andvariations that fall within the scope of the included claims. Allmatters set forth herein or shown in the accompanying drawings are to beinterpreted in an illustrative and non-limiting sense.

What is claimed is:
 1. A method of operating a cloud computing systemcomprising: receiving, by one or more computing devices, a configurationfile from a configuration repository, wherein the configuration filecontains instructions for configuring an application rule set of one ormore nodes in a network; monitoring, by the one or more computingdevices and by continuously checking a plurality of devices, theplurality of devices for a request from at least one of the plurality ofdevices, wherein the request indicates the at least one of the pluralityof devices is requesting to configure the application rule set of theone or more nodes based on the configuration file; transmitting, by theone or more computing devices, the request to a receiver node selectedfrom the one or more nodes, wherein the receiver node further transmitsthe request to a message service for storage on a database; generating,by the one or more computing devices, a notification, wherein thenotification alerts the one or more nodes that the request is stored onthe database; distributing, by the one or more computing devices, theconfiguration file to a subset of the one or more nodes based on receiptof an access request from the one or more nodes in response to thenotification, wherein the access request requests access to theconfiguration file; and updating, by the one or more computing devices,the application rule set of the subset of the one or more nodes based onthe configuration file.
 2. The method of claim 1, wherein the monitoringfurther comprises sending one or more pull requests at specified timesto the plurality of devices to check for the request.
 3. The method ofclaim 1, wherein the request is stored on the at least one of theplurality of devices.
 4. The method of claim 1, further comprising:selecting, by the one or more computing devices, the receiver node fromthe one or more nodes based on analyzing one of a processor speed, aprocessor bandwidth, a node storage capacity of the one or more nodes,and wherein the selecting is based on: the receiver node having thefastest processing speed amongst the one or more nodes, the receivernode having the most bandwidth to process data amongst the one or morenodes, or the receiver node having the most storage capacity amongst theone or more nodes.
 5. The method of claim 1, wherein the configurationfile configures the application rule set to control a method ofcommunication by the one or more nodes to one or more external users,wherein the method of communication comprises: an email communication, atext message, or a push notification.
 6. The method of claim 1, whereindistributing the configuration file to the subset of the one or morenodes includes distributing the configuration file to all of the one ormore nodes in the subset of the one or more nodes.
 7. The method ofclaim 1, wherein updating the application rule set of the subset of theone or more nodes based on the configuration file includes updating theapplication rule set of all of the subset of the one or more nodes.
 8. Anon-transitory computer readable medium having instructions storedthereon that, when executed by a cloud computing system, cause the cloudcomputing system to perform operations comprising: receiving aconfiguration file from a configuration repository, wherein theconfiguration file contains instructions for configuring an applicationrule set of one or more nodes in a network; monitoring, by continuouslychecking a plurality of devices, the plurality of devices for a requestfrom at least one of the plurality of devices, wherein the requestindicates the at least one of the plurality of devices is requesting toconfigure the application rule set of the one or more nodes based on theconfiguration file; transmitting the request to a receiver node selectedfrom the one or more nodes, wherein the receiver node further transmitsthe request to a message service for storage on a database; generating anotification, wherein the notification alerts the one or more nodes thatthe request is stored on the database; distributing the configurationfile to a subset of the one or more nodes based on receipt of an accessrequest from the one or more nodes in response to the notification,wherein the access request requests access to the configuration file;and updating the application rule set of the subset of the one or morenodes based on the configuration file.
 9. The non-transitory computerreadable medium of claim 8, the operations further comprising monitoringby sending one or more pull requests at specified times to the pluralityof devices to check for the request.
 10. The non-transitory computerreadable medium of claim 8, wherein the request is stored on the atleast one of the plurality of devices.
 11. The non-transitory computerreadable medium of claim 8, the operations further comprising:selecting, by the one or more computing devices, the receiver node fromthe one or more nodes based on analyzing one of a processor speed, aprocessor bandwidth, a node storage capacity of the one or more nodes,and wherein the selecting is based on: the receiver node having thefastest processing speed amongst the one or more nodes, the receivernode having the most bandwidth to process data amongst the one or morenodes, or the receiver node having the most storage capacity amongst theone or more nodes.
 12. The non-transitory computer readable medium ofclaim 8, wherein the configuration file configures the application ruleset to control a method of communication by the one or more nodes to oneor more external users, wherein the method of communication comprises:an email communication, a text message, or a push notification.
 13. Thenon-transitory computer readable medium of claim 8, wherein distributingthe configuration file to the subset of the one or more nodes includesdistributing the configuration file to all of the one or more nodes inthe subset of the one or more nodes.
 14. The non-transitory computerreadable medium of claim 8, wherein updating the application rule set ofthe subset of the one or more nodes based on the configuration fileincludes updating the application rule set of all of the subset of theone or more nodes.
 15. A cloud computing system comprising: acommunication unit configured to: receive a configuration file from aconfiguration repository, wherein the configuration file containsinstructions for configuring an application rule set of one or morenodes in a network; transmit a request to a receiver node selected fromthe one or more nodes, wherein the receiver node further transmits therequest to a message service for storage on a database; and a controlunit, coupled to the communication unit, configured to: monitor, bycontinuously checking a plurality of devices, the plurality of devicesfor the request from at least one of the plurality of devices, whereinthe request indicates the at least one of the plurality of devices isrequesting to configure the application rule set of the one or morenodes based on the configuration file; generate a notification, whereinthe notification alerts the one or more nodes that the request is storedon the database; distribute the configuration file to a subset of theone or more nodes based on receipt of an access request from the one ormore nodes in response to the notification, wherein the access requestrequests access to the configuration file; and update the applicationrule set of the subset of the one or more nodes based on theconfiguration file.
 16. The cloud computing system of claim 15, whereinthe control unit is further configured to monitor by send one or morepull requests at specified times to the plurality of devices to checkfor the request.
 17. The cloud computing system of claim 15, wherein therequest is stored on the at least one of the plurality of devices. 18.The cloud computing system of claim 15, wherein the configuration fileconfigures the application rule set to control a method of communicationby the one or more nodes to one or more external users, wherein themethod of communication comprises: an email communication, a textmessage, or a push notification.
 19. The cloud computing system of claim15, wherein the control unit is further configured distribute theconfiguration file to the subset of the one or more nodes bydistributing the configuration file to all of the one or more nodes inthe subset of the one or more node.
 20. The cloud computing system ofclaim 15, wherein the control unit is further configured to update theapplication rule set of the subset of the one or more nodes based on theconfiguration file by updating the application rule set of all of thesubset of the one or more nodes.